Sigcat 1994: Conference Disk

home *** CD-ROM | disk | FTP | other *** search

/ Sigcat 1994: Conference Disk / SIGCAT 94 Conference Disk - DataDisc.ISO / interdos / disk1.exe / README.DOC < prev next >

Wrap

Text File | 1994-03-02 | 43.2 KB | 1,068 lines

The Dos Internet Kit Packaged by: Dean Pentcheff ( dean2@tbone.biol.scarolina.edu) What is this? This is a collection of public domain programs that enable Ethernet or serially-connected PCs to access Internet services. It is packaged as a relatively easy to install kit to help people get started. In this (and the following) documentation are instructions on downloading the Internet Kit, installing it on a PC, and configuring all the software. Revision history for the Kit March 2, 1994 Updated Windows Mosaic to version 2.0 alpha 2. February 26, 1994 Updated Winsock to Release 1.0, added Winsock's winapps, updated packet driver Version 11 with 12/14/93 updates, updated Windows Mosaic to Release 2.0alpha1, updated NCSA telnet to 2.3.07b. December 19, 1993 Really updated Winsock to Alpha 18 (last time, I mistakenly left Alpha 17 in place), fixed bug on Winsock line in install.002 script. December 12, 1993 Updated Winsock to Alpha 18 (SLIP scripting), updated packet drivers to Version 11, and fixed a bug in install script that prevented installation of the 3c503.com driver. November 19-20, 1993 Fixed wrong ftp filename in 3c503 document (thanks Russ Nelson!) and switched to new 3c503.com that doesn't require shared memory. November 13, 1993 Added the full set of Crynwr packet drivers. Updated Trumpet Winsock to alpha 17 (with SLIP support), NCSA Windows Mosaic to 1.0, and LView to 3.1. November 8, 1993 First release. Included 3c503 driver from Crynwr 1.0, NCSA Telnet 2.3.06 (with added tn3270 program), Telnet documentation, PC Gopher III 1.1.2, Trumpet Winsock alpha 16, NCSA Windows Mosaic beta 0.7b, and LView 3.0. This is the documentation for a set of two floppy disks that contain a kit of programs for connecting PCs to the Internet. A plain-text version of the documentation is in the file readme.doc on Disk 1 of the Kit. The rationale behind the Kit is described at the end of this document. This kit is available using the Internet World Wide Web at the site tbone.biol.scarolina.edu Use a WWW browser to connect to the HTTP server at that site and check the Home Page (index.html) for the "PC Internet Kit" entry. At that site are also the hypertext versions of the installation hints included below. If you experience difficulty downloading files using a hypertext browser, you can also fetch them by anonymous FTP from the server tbone.biol.scarolina.edu in directory /pub/kit. See the file 00README.DOC in that directory for instructions on which files to grab and how to unpack them onto floppy disks. If you are reading this document using a hypertext browser (like NCSA Mosaic) then you can follow highlighted passages (like the previous parenthesized statement) through the network to their location. A highlighted filename will fetch the file, a highlighted directory name will display a menu of the files in the directory. If you're reading this on paper or in plain text from the floppy disk readme.doc file, then it's time you used it to set yourself up with a hypertext browser so that you can use this document properly! Onwards... Fetching and Arranging The Floppy Disk Files The Kit is designed to fit onto two 1.44 Mb floppy disks. Hence, (if you are reading this as hypertext) this document has hyperlinks to two binary files, each holding the files intended for one floppy disk. If you are reading this as plain text and you already have the files on floppies, skip to the section below on Installing the Files. If you are reading this text using a hypertext browser, links to the two self-extracting disk files follow this paragraph. Each disk's files are in a self-extracting zip file. Arrange your browser to load these files to your local disk, then click on them one by one to fetch them. disk1.exe disk2.exe Once you have both of those files on your local hard disk you need to create the installation floppy disks from them. Put a blank, formatted, 1.44 Mb floppy disk into your floppy drive (I'll assume your hard disk is C: and your floppy drive is A:. If not, modify the following instructions appropriately). Change to that drive and then run disk1.exe (the first self-extracting file). For example: C> a: A> c:disk1 The files will be unpacked onto the floppy disk. Repeat (with another floppy disk) for the second self-extracting file (disk2.exe). The files on disk 1 are: README.DOC Documentation file 3C503.COM Packet driver for the 3Com 3c503 Ethernet board 3C503.DOC Documentation note for 3c503.com and other packet drivers CONFIG.TEL Configuration file for NCSA Telnet TEL2307B.ZIP NCSA Telnet archive file INSTALL.001 Installation program script for the first disk INSTALL.EXE Installation program PKUNZIP.EXE Installation program for unpacking archive files CHDRIVE.EXE Installation program used to change current drive/directory YORN.EXE Installation program for getting a Y or N from the user NEW_PKT.BAT Installation batch file for installing 3c503.com NEW_TEL.BAT Installation batch file for installing config.tel UNPACK.BAT Installation batch file for running pkunzip.exe appropriately The files on disk 2 are: PKTD11.ZIP The complete set of Clarkson/Crynwr packet drivers PCGOPH3.ZIP DOS Gopher III archive file LVIEW31.ZIP Windows image viewing and manipulation program archive file WINSOCK.ZIP Trumpet Winsock archive file WINAPPS.ZIP Some applications using Trumpet Winsock WMOS20a1.ZIP Windows version of NCSA Mosaic INSTALL.002 Installation program script for the second disk PKUNZIP.EXE Installation program for unpacking archive files CHDRIVE.EXE Installation program used to change current drive/directory UNPACK.BAT Installation batch file for running pkunzip.exe appropriately Installing the Files The files are installed from the floppies using an installation scripting program that I got from the net (Jeff Dunlop's Install-Pro 1.64, available by FTP from oak.oakland.edu and other fine SIMTEL FTP mirror sites). If you want to be able to use that script, you must arrange the files as they are given, on two floppies. Otherwise, you'll have to unzip and copy the files manually. Insert Disk 1 into your PC's floppy drive, then switch your current drive to that drive, and run "install" (do this under DOS, not under Windows). For example, if the floppy disk was put into drive A:, then you would do the following: C:\> a: A:\> install Do not try to run the install program on the floppy while your current drive is still the hard drive - make sure to switch to the floppy drive first. The installation program will ask you which parts of the whole set to install, and will give you a chance to set your own destination directories on your hard drive. What to install Here's a little outline of my suggestions on what to install, followed by a few words of rationalization for each of the choices. Once you've installed files, follow the specific configuration instructions below. The software will not work without proper configuration. Furthermore, you should install the software in the order presented. And, just to make sure I get it across: read the installation documents I've provided to install the software properly, or it will not work. Do you have a 3Com 3c503 Ethernet board? Yes: Install "New 3c503.com Packet Driver" Don't install "All Packet Drivers" No: Install "All Packet Drivers" Don't install "New 3c503.com Packet Driver" Do you want DOS (character-mode) telnet, ftp, etc.? Yes: Install "DOS NCSA Telnet" Was NCSA Telnet previously installed on your computer? Yes: Don't install "New NCSA Config File" No: Install "New NCSA Config File" No: Don't install "DOS NCSA Telnet" Don't install "New NCSA Config File" Do you run Windows 3.1 on your computer? Yes: Don't install "DOS Gopher" Install "Winsock (for Mosaic)" Install "Winapps (with Winsock)" Install "Windows Mosaic" Install "GIF Viewer (for Mosaic)" No: Install "DOS Gopher" Don't install "Winsock (for Mosaic)" Don't install "Winapps (with Winsock)" Don't install "Windows Mosaic" Don't install "GIF Viewer (for Mosaic)" A few details on why to install various parts New 3c503 Packet Driver: Because nearly everyone in the department here (at USC in Columbia, SC) has a PC with a 3Com 3C503 Ethenet board, this is the packet driver I've included. If you have an older 3C503.com packet driver, load this new one. If you have a different Ethernet board, then do not load this packet driver, but load the All Packet Drivers selection. All Packet Drivers: This is the entire kit of packet drivers for many different Ethernet boards. Load this if you don't have a 3C503 Ethernet board. Following the software installation, search through these drivers and their accompanying documentation to find the one appropriate for your Ethernet board. Install it in the C:\NCSA directory, just as the 3C503 driver would have been installed. The specifics of the driver command line and configuration will be different from the 3C503 instructions, but you can use them as a guide for how to configure and load your packet driver. Just modify the command arguments as appropriate for your driver. Of course, once you've selected and installed your packet driver, you can delete all the others from your hard drive. DOS NCSA Telnet: Load this package to get DOS character-mode programs that will allow you to log into a remote computer (telnet) and transfer files to and from remote computers (FTP). New NCSA Config File: Load this if you do not have a pre-existing version of NCSA telnet. If you already have a version of NCSA telnet, don't load this file, as your old configuration information will get overwritten. DOS Gopher: Load this if you do not run Windows and do not plan to load Mosaic. If you will be running Mosaic, then there's little reason to run a DOS Gopher program as well. You can access Gopher servers using Windows Mosaic. Winsock (for Mosaic): Load this if you plan to run Windows Mosaic. To run Mosaic, you'll need to load a packet driver for your Ethernet board and the Winsock driver. If you will be using a SLIP connection for Mosaic (that is, you'll be dialing in using a modem and connecting with a serial line networking server), then you can use Winsock without a packet driver - it now has a builtin SLIP capability. Winapps (with Winsock): Load this if you've loaded Trumpet Winsock. It contains some TCP/IP programs (similar to ones in the NCSA Telnet package) that may be helpful to you. Windows Mosaic: If you run Windows, load this. It is the easiest interface program to the resources of the Internet. GIF Viewer (for Mosaic): Load this if you load Windows Mosaic. Mosaic will use this program to display image files from the Internet. Specific Installation Hints If you are reading this online as a hypertext document, follow the links below to the documents. If this is a plaintext copy, these documents are appended below. Some locally useful information Installation hints for the 3c503.com packet driver Installation hints for NCSA Telnet Installation hints for PC Gopher Installation hints for Trumpet Winsock and Winapps Installation hints for Windows Mosaic Installation hints for LView Why This Internet Kit? There are many DOS machines out there that already have an Ethernet (or equivalent) connection to the worldwide Internet. Recently, there has been an outpouring of new, very appealing ways to explore the resources available on the Internet. These include, most notably, Gopher and NCSA Mosaic. Both of these are available for PCs running DOS and Windows. The problem for many people has been one of understanding how to get it all installed. Software X seems to require package Y before it will run, but where do I find Y? And then how do I configure X, since it seems to have no documentation?... On the other hand, initial help can be hard to get: for those of us who have had the perversity to struggle through and figure it out (more or less), the time involved in setting up a new Internet-naut can be prohibitively large. Let's not even think about setting up a whole department or large office of people. Hence, this DOS Internet Kit. I've tried to put together a (fairly) painless way to install the basic parts that will permit a PC which already has an Ethernet or similar connection to take advantage of some of the new software. I make all sorts of assumptions about local hardware - these will have to be modified on a per-site basis. I've included some locally useful information about gateways, nameservers, etc., and that will certainly need to be changed for folk elsewhere. I hope this is useful to some folks out there - please let me know if it is. On the other hand, please send me suggestions on how I can improve this offering (bearing in mind that I've already spent far too much time doing this)! My email address is at the bottom of this document. ==================================================================== Some locally useful information Warning: this section contains information local to computers at the University of South Carolina, Columbia, South Carolina, USA (and particularly the Biological Sciences and Geology departments there). These specific numbers won't work unless you're there. Nameservers (IP number and name) 129.252.31.2 epoch.geol.scarolina.edu 129.252.43.9 theusc.csd.scarolina.edu 129.252.42.25 sparky.csd.scarolina.edu 129.252.11.9 usceast.cs.scarolina.edu Gateways (IP number and name) 129.252.34.1 biol-gate.geol.scarolina.edu 129.252.31.1 geol-gate.biol.scarolina.edu Netmask (this is probably correct, but make sure it's right for you) 255.255.255.0 Domains (you must know which is yours, these are examples!) biol.scarolina.edu geol.scarolina.edu Your machine's IP number I can't tell you that - you must get it from your network administrator. ==================================================================== Installation Hints for the 3c503 Packet Driver Software Release This document is based on Release 11 of the Crynwr (nee Clarkson) Packet Drivers. Software Purpose A packet driver provides a standardized way for network software to access your network hardware. Many network sofware packages are written assuming that you have already loaded a packet driver to mediate between the software and your network board. Assumptions You have a 3Com 3C503 Ethernet board in your computer. No kidding, here. These instructions are specific to that board and that particular packet driver. These hints are being written primarily for our local users here at USC in South Carolina, and that's what most people here have. If you have a different Ethernet board, then you'll need to use a different packet driver from the full collection of Crynwr packet drivers (see the Where To Get Updates section at the bottom of this document). You can use this document to help guide your installation of a different packet driver, but be sure to use the packet driver arguments that are appropriate for your driver: see that driver's installation notes from the full Crynwr packet driver distribution. With a different card, you will have a line inserted in your \AUTOEXEC.BAT file that is different from the one described below. You have loaded the 3c503.com file into the directory \NCSA. This directory name is not required, it's just what I'm assuming here. You are using the following hardware settings (unless mentioned otherwise, you can select other settings as long as you modify the following hints appropriately). Again note: this is specific to the 3c503 board and driver: check the documentation for your board's packet driver if you are using a different one. Your 3C503 board is connected using Thinnet (10Base-2) cabling. That is, your Ethernet connection is to the single-wire barrel connector on the back of the Ethernet card (a BNC connector), not to the multipin connector that's also there (the AUI connector). You have set the 3C503 board's "straps" (little black plastic jumpers on the board) as follows: I/O port address of 0x300. You have set the shared memory straps to any value (which could include "disabled"). NOTE: Older versions of the 3c503 driver required that shared memory be set to something other than "disabled". The version distributed here will automatically accomodate "disabled". You are going to use software interrupt level 0x78 (conventional if you will be using a Novell network as well). You will use interrupt level 2. Select an interrupt level that does not conflict with anything else on your computer. Your choices are: 2, 3, 4, or 5. Those interrupts might also be used by: 2: Second PC timer interrupt (try this one for the 3c503). 3: Serial ports 2 and 4 (if you have them). 4: Serial ports 1 and 3 (you usually have serial port 1). 5: Parallel port 2 (which you may not have - if not, this is a good alternative to IRQ 2 for the 3c503). Installation Hints Insert a line in your \AUTOEXEC.BAT file to load the 3c503 driver (or make sure that an existing line like this has the right directory path and settings). It should look like the following (given the assumptions above): c:\ncsa\3c503.com 0x78 2 0x300 1 That loads the driver from the \NCSA subdirectory and tells it to use: software interrupt number 0x78; interrupt level 2; I/O port 0x300; and thinnet rather than AUI (the last number would be "0" for AUI). The weird looking numbers (e.g. 0x78) are prefixed with "0x" to tell the driver to interpret them as hexadecimal (base 16) rather than as decimal (base 10) numbers. Check around on your computer to see if there are any other old copies of the 3c503.com driver hanging around. They may be in the root directory (not in a subdirectory at all, but hanging around in the same directory as \AUTOEXEC.BAT and \CONFIG.SYS), or directories named NOVELL, or NET, etc. If you find an old driver, rename it to 3c503.old so that you hold onto it (just in case!) but it can't be run. If you have batch files that load network applications, edit them to delete any lines that might have loaded the old 3c503.com driver. You don't need to reload the driver when executing those files, since it is already loaded at boot time, so just remove lines that attempt to reload it. Such files might be called net.bat, network.bat, logon.bat, etc. and might be in the same network-related directories as mentioned in the previous hint. Notable Bugs Where To Get Updates The Crynwr packet driver kit (which includes drivers for many other boards) is available via anonymous FTP from the host oak.oakland.edu in directory /pub/msdos/pktdrvr in binary file pktd11.zip The updates in pktd11c.zip have been added to the version distributed from tbone.biol.scarolina.edu. NOTE: It is quite likely that the name of the binary file(s) or even the directory name(s) may change over time as the software is updated. Be prepared to poke around a little if you don't find things exactly as I've described. ==================================================================== Installation hints for NCSA Telnet Software Release This document is based on Release 2.3.07 of the NCSA Telnet package. (Note - if you are using the version distributed from tbone.biol.scarolina.edu, we have added some tn3270 programs to the base NCSA package, as well as slightly editing the "config.sys" file to include local gateways, etc.) Software Purpose Provides character-oriented TCP/IP abilities for PC computers under DOS. This includes programs such as telnet, ftp, lpr, etc. Assumptions You have successfully loaded a DOS packet driver for your Ethernet board. You know your machine's IP number. You know your IP domain name, your local netmask, and IP numbers for local network gateways, and nameservers. (If you are at USC in South Carolina, you might want to refer to our list of locally useful values.) You have unpacked the NCSA Telnet distribution files into a directory called C:\NCSA (this is not required, but that's what I'm assuming below). Installation Hints Make sure that the PATH statement in your \AUTOEXEC.BAT file contains the path to the NCSA software. Edit the batch files telnet.bat and tn.bat in the NCSA directory. If you have a host to which you will often be connecting, change the dummy computer name void that appears in some of the batch files to the name of your frequent host. That way if you type the name of the batch file without a host name, it will automatically use that host. In the installation directory, edit the file config.tel. Check the following items (if you're at USC, you may want to refer to the list of locally useful values): myip= Should be set to the IP address of your PC. netmask= Should be set to your network's netmask. hardware/address/etc. I'm assuming that you are using a board with a packet driver. In that case, do the following: Make sure there's a hash mark ("#") in front of all the "hardware", "address", "ioaddr", and "interrupt" lines except the one that reads "hardware=packet". Make sure that the "hardware=packet" lines look like the following: hardware=packet ioaddr=78 interrupt=2 NOTE that the "ioaddr" number must agree with the ioaddr number you supplied to your packet driver, and the "interrupt" number must agree with the interrupt number you supplied. These are usually on a line in your \AUTOEXEC.BAT file. myname= Should be set to the name of your PC. This setting is not crucial, so if you don't know, don't worry. keyfile= Make sure that the path here points correctly to the directory in which you installed the NCSA Telnet software. domain= Should be set to the domain part of your full machine name. For example, if your machine is called mymachine.biol.scarolina.edu then your domain is biol.scarolina.edu color settings There are a set of color settings following the name=default entry toward the bottom of the config.tel file. You can leave these as they are, or change them at will. I swear by the following (of course, you may swear at them): nfcolor=WHITE nbcolor=blue rfcolor=blue rbcolor=white ufcolor=YELLOW ubcolor=blue gateway/nameserver entries At the bottom of the config.tel file are a list of computer names and IP addresses that the telnet package will recognize. Fill these in with locally useful names. Following the pattern of the machines in the config.tel file, fill in at least one entry for a nameserver and one entry for a gateway machine. You'll have to get these addresses and names from your local network adminstrator. Notable Bugs Where To Get Updates This software is maintained by the National Center for Supercomputing Applications (developer of much great, free software). The package can be retrieved using anonymous FTP from the host ftp.ncsa.uiuc.edu in the directory /Telnet/msdos in the binary file tel2307b.zip. Documentation is at the same site in directory /Telnet/msdos/docs in the binary file tel23asc.zip. NOTE: It is quite likely that the name of the binary file(s) or even the directory name(s) may change over time as the software is updated. Be prepared to poke around a little if you don't find things exactly as I've described. ==================================================================== Installation hints for PC Gopher Software Release This document is based on PC Gopher III Version 1.1.2. Software Purpose PC Gopher is a DOS character-mode program that permits a PC to connect to and explore the interlinked network of Gopher menus and documents around the Internet. If you are going to use Windows Mosaic, then you really don't need PC Gopher. Mosaic can access Gopher servers at least as easily as can PC Gopher. Assumptions You have successfully loaded a DOS packet driver for your Ethernet board. You know your machine's IP number. You know your IP domain name, your local netmask, and IP numbers for local network gateways, and nameservers. (If you are at USC in South Carolina, you might want to refer to our list of locally useful values). You have unpacked the NCSA Telnet distribution files into a directory called C:\NCSA (this is not required, but that's what I'm assuming below). This is because Gopher will call some NCSA Telnet programs to make telnet and tn3270 connections to some hosts. You have unpacked the PC Gopher files into a directory called C:\gopher (this is not required, but that's what I'm assuming below). Installation Hints Make sure that the PATH statement in your \AUTOEXEC.BAT file contains the path to the PC Gopher software directory. Change directories to the PC Gopher directory and start it by giving the command gopher Press the Alt-C key to enter the Configuration menu, then select the Application choice. On that screen, make the following changes: Home Gopher Server: If you wish, you can change this to the name of a gopher server at your own institution. At USC, change this to hare.csd.scarolina.edu In rare cases, you may need to change the port number to something different from "70". Don't change it unless you know you need to. Alternate Server: If you changed the "Home Gopher Server" you may wish to set this to gopher.tc.umn.edu Telnet Session Command Line: If you set up NCSA Telnet properly, with the proper paths in NCSA Telnet's telnet.bat and tn.bat batch files, then you can simplify this line to: telnet $a#$p Since the NCSA telnet directory is on your PATH list, the proper batch file will be found automatically. tn3270 Session Command Line: Similarly, this line may be simplified to: tn $a#$p (By the way, the "$a#$p" is not a typo: when Gopher calls these programs it will replace "$a" with the name of the host to contact and "$p" with the port number to use.) [ ] New Gopher on Startup: Until you are sure your Gopher installation is working, make sure there is not an "X" in this box. Now, press Alt-K for "OK" and exit that screen. Press the Alt-C key to enter the Configuration menu, then select the Network choice. On that screen, make the following changes. (Again, if you are at USC in South Carolina, you might want to refer to our list of locally useful values). Microcomputer IP Address: Fill in the IP address of your PC. Microcomputer Netmask: Fill in the netmask for your local network. [ ] Use BOOTP: Unless you know you use the BOOTP protocol to get your machine's IP address, make sure that this box does not have an "X" in it. Gateways: Fill in the IP address of at least one locally available gateway (preferrably more). Name Servers: Fill in the IP address of at least one locally available nameserver (preferrably more). Now, press Alt-K for "OK" and exit that screen. Try the new setup by pressing Alt-F for the File menu, and then select "New Gopher". If it works, you'll see the menu of a gopher server on your screen (possibly after some seconds while the network connection is made). If it doesn't, review the configuration parameters, making sure that you made no typos in the IP addresses in the Network configuration. Once it does work, you may want to check off the "New Gopher on Startup" box in the Configure/Application screen. After you quit the Gopher program, edit the file gopher.ini in the Gopher program directory. Find the line that begins with bookmark_file = and change it to: bookmark_file = c:\gopher\gopher.bmk (assuming your gopher programs are in the c:\gopher directory). That way you will access the same Bookmark file no matter what directory you are in when you start Gopher. Notable Bugs Like many network programs, Gopher will occasionally hang when a network read goes awry or a remote host is down. Time for the three-finger salute (but give Gopher a chance to time-out and recover - perhaps up to a minute). Where To Get Updates Note: if you got this package from tbone.biol.scarolina.edu, we slightly modified the "official" distribution package. We removed a couple of programs for converting bookmark and initialization files of old versions of PC Gopher, and inserted the main PC Gopher documentation into the parcel. So, if you fetch the "official" versions, be sure to fetch both the program files and the documentation files. This software was written at the University of Minnesota. The package can be retrieved using anonymous FTP from the host boombox.micro.umn.edu in the directory /pub/gopher/PC_client in the binary file pcg3bin.zip. Documentation is at the same site and directory in the binary file pcg3doc.zip. Note: This FTP retrieval may not work from within a hypertext browser (it appears to be broken from within WMosaic Alpha 0.7, but works in XMosaic). If that's the case, just use normal FTP or Gopher itself to fetch the file from boombox.micro.umn.edu. NOTE: It is quite likely that the name of the binary file(s) or even the directory name(s) may change over time as the software is updated. Be prepared to poke around a little if you don't find things exactly as I've described. ==================================================================== Installation hints for Trumpet Winsock and Winapps Software Release This document is based on Peter Tattam's Trumpet Winsock Release 1.0. NOTE: Trumpet Winsock and the accompanying Winapps are not freeware or public-domain. You may try them out and distribute them freely, but if you use this software, please see its accompanying documentation regarding registration fees (which are nominal). Please help support one of the hard-working programmers making network access easier for all the rest of us! Software Purpose Trumpet Winsock is a shareware Winsock 1.1 driver. It provides a TCP/IP connection layer between MS Windows and an underlying DOS packet driver. Basically, it allows you to run network programs under Windows (as long as they have been written for the "Winsock" standard). The Winapps package accompanying it contains some useful TCP/IP programs. I won't go into them in detail here. Assumptions You have successfully loaded a DOS packet driver for your Ethernet board. That packet driver is loaded and run from your \AUTOEXEC.BAT file. You know your machine's IP number. You know your IP domain name, your local netmask, and IP numbers for local network gateways, and nameservers. If you are at USC in South Carolina, you might want to look at a listing of locally useful information. You have unpacked the Winsock distribution files into a directory called c:\winsock (this is not required, but that's what I'm assuming below). Similarly, you have unpacked the programs in the Winapps package into the same directory. Your machine runs Windows 3.1. Note:The Winsock driver supports access over SLIP (serial line IP) as well as over an Ethernet packet driver. This means that you could use Winsock (and hence Mosaic or other Winsock-dependent programs) over a modem and phone line instead of a direct-wired Ethernet connection. You have to know of a SLIP-capable host to which you will connect, and have a means of dialing up, logging in, and starting the host-side SLIP connection. Then you can invoke Winsock in SLIP mode and it will talk to the host over the phone line. Our users here are primarily hard-wired, so this discussion is oriented towards the regular non-SLIP usage. If you are going to use SLIP, then ignore any discussion of the packet drivers in \AUTOEXEC.BAT, and select the SLIP option when you are configuring tcpman.exe (see below). See the more detailed installation instructions provided with the Winsock driver in the file install.txt (which should get installed in the same directory as the Winsock software). Installation Hints Insert a line in your \AUTOEXEC.BAT file that will load the virtual packet driver immediately after your Ethernet board packet driver. For example, if you are using the 3com 3c503 Ethernet board with fairly generic settings, you would have the following packet driver line in your \AUTOEXEC.BAT file: c:\ncsa\3c503.com 0x78 2 0x300 1 Add the following line right after it to load the virtual packet driver: c:\winsock\winpkt.com 0x78 Notice that you supply the same software interrupt number to the virtual packet driver that you gave to your packet driver. Add the Winsock directory to your path list in \AUTOEXEC.BAT. Reboot the machine to get the new PATH working. As the machine boots, you should also see the packet driver load, follwed immediately by the new virtual packet driver. Start Windows. Add a Group Item (if you wish) for Winsock, and create a Program Item icon for the program c:\winsock\tcpman.exe . Set the Working Directory to the c:\winsock directory. Start tcpman.exe. It will ask you for some configuration information. (Again, if you are at USC in South Carolina, you might want to look at a listing of locally useful information.) IP address: Enter the IP address of your PC. Netmask: Enter the netmask for your local network. Default Gateway: Enter the IP number for a local gateway. Name server: Enter the IP number for a local nameserver. Timeserver: Leave this blank - it's currently unused. Domain Suffix: Enter the local domain name. For example, if your machine's name is tbone.biol.scarolina.edu your domain is biol.scarolina.edu. Internal SLIP, SLIP Port, Baud Rate: Leave these unchecked and empty unless you are using a SLIP (modem/phone) connection instead of a direct Ethernet connection. (If so, see the detailed instructions for SLIP included in the file install.txt with the driver.) Press the "OK" button, and that should be that. As long as Winsock started nicely, you should see a boring-looking text screen telling you that Winsock is running. You can stop it by double-clicking the top-left corner button (the normal Windows kill button). In normal use, Winsock is automatically loaded by programs that need it (and kept iconized, so you don't even see its screen), so you never have to run it yourself. From the Windows Program Manager, create Program Items for the programs distributed in the Winapps package. Put them where you wish (if you created one, the Winsock Group window would be a good place). Notable Bugs Pretty darned solid, as far as I can tell. Where To Get Updates There is a hypertext page to help you retrieve the most recent versions of Winsock and Winapps at http://info.utas.edu.au/ftp/pc/trumpet/winsock/winsock.html. Alternately, if you want to do it "manually" using FTP, you can use anonymous FTP to the host biochemistry.bioc.cwru.edu in directory /pub/trumpwsk/ in binary files winsock.zip and winapps.zip. For convenience, I have combined the contents of these two files into this distribution's winsock.zip file. NOTE: apparently this is a weird FTP server that may not work from within a WWW browser like NCSA Mosaic. Use the hypertext page mentioned above to FTP the package if you are using a hypertext browser, or just use regular FTP to the biochemistry.bioc.cwru.edu host. Once again, please note that Trumpet Winsock is not free, it is shareware (with a nominal registration fee). Please see its documentation for further details. NOTE: It is quite likely that the name of the binary file(s) or even the directory name(s) may change over time as the software is updated. Be prepared to poke around a little if you don't find things exactly as I've described. ==================================================================== Installation hints for Windows Mosaic Software Release This document is based on NCSA Mosaic for Windows release 2.0 Alpha 2. Software Purpose NCSA Mosaic is an interface to the World Wide Web hypertext system extending across the Internet. It is capable of navigating through, displaying, and fetching: WWW documents, (including inline images), Gopher servers, WAIS servers, and FTP hosts, among other resources. Assumptions You have successfully loaded a DOS packet driver for your Ethernet board. You have successfully loaded a Winsock 1.1 compliant virtual packet driver before launching Windows. (Alternately to these two assumptions, you may be using a SLIP version of a Winsock driver over a modem and phone line). Your machine runs Windows 3.1. You have unpacked the Mosaic files in a directory called c:\mosaic (this directory name is not required, but that's what I'm assuming below). You have installed (or will install) the image viewer LView in the directory \lview. This is not required, but it is helpful to have an "external" image viewing program for image files. If you have a different program you'd like to use, or your viewer is in a different directory, appropriately modify the instructions below for supplying the image viewer's path. Installation Hints If you'd prefer, there is an "official" set of installation instructions for Mosaic available with the package. Consider this document as a "quick start" version. From the Mosaic installation directory, copy the file mosaic.ini to your main Windows directory (usually \windows). Edit the \windows\mosaic.ini file and check the following entries: E-mail: If you have an email address, supply it here. Autoload Home Page: If you'd like the "home page" to appear immediately, set this to "yes". Home Page: Set this to the location of the home page you would like to load. If you don't know of a local or special home page you'd like to load, leave this line as it is. For example, we set our machines to: Home Page="http://tbone.biol.scarolina.edu/" [skip down in the file] image/gif and image/jpeg: Set both of these to the full path name of your Windows image viewer program. For example, you might set these to: image/gif="c:\lview\lview31 %ls" image/jpeg="c:\lview\lview31 %ls" Make sure to retain the "%ls" at the end of each line. From within Windows, create a Program Group object (if you wish) and a Program Item object for Mosaic. Set the Working Directory to be the directory into which you installed Mosaic. Once the program is running, if you change the size or position of the window, pull down File/Save Window Postion to fix those changes in place. Notable Bugs A few assorted oddities: but it's an Alpha release, after all... Check frequently for updates - the good people at NCSA are working very hard on this program. Where To Get Updates NCSA Mosaic (available for Windows, Mac, and X Windows) is another superb software product of the National Center for Supercomputing Applications. The Mosaic distribution directory is available via anonymous FTP on host ftp.ncsa.uiuc.edu in directory /Mosaic. Windows Mosaic specifically is available in the directory /Mosaic/Windows in the binary file wmos20a2.zip. NOTE: It is quite likely that the name of the binary file(s) or even the directory name(s) may change over time as the software is updated. Be prepared to poke around a little if you don't find things exactly as I've described. ==================================================================== Installation hints for LView Software Release This document is based on LView 3.1. Software Purpose LView is an image file viewer and manipulator for MS Windows. It can be used as an "external" image file viewer by other Windows programs (notably WMosaic). Assumptions You are running Windows 3.1 with a decent color display. You have unpacked the LView files in a directory called c:\lview (this is not required, but that's what I'm assuming below). Installation Hints From within Windows, create a Program Group object (if you wish) and a Program Item object for LView. That's all. Of course, there are other setup options you can tweak from within LView, but this will certainly work fine to get you started. Notable Bugs Some types of images (JPEG) generate error messages as they load - acknowledge the messages and the images will display. This program uses an unregistered version of wecjlib.dll from Express Compression Laboratories which complains. For better performance and to avoid the error messages, you could register your copy of wecjlib.dll. Alternately, just live with it - the images display OK. Where To Get Updates LView is available via anonymous FTP from the host oak.oakland.edu in directory /pub/msdos/windows3 in binary file lview31.zip NOTE: It is quite likely that the name of the binary file(s) or even the directory name(s) may change over time as the software is updated. Be prepared to poke around a little if you don't find things exactly as I've described. ==================================================================== Dean Pentcheff, dean2@tbone.biol.scarolina.edu (803) 777-8998 Biological Sciences, University of South Carolina, Columbia SC 29208 USA